Merged
Conversation
1af09d1 to
6457365
Compare
Member
|
@BobbieGoede |
kazupon
approved these changes
Dec 4, 2023
Member
Author
|
Such a strange error on the first e2e install run, maybe it was too quick after release? 😂 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Not sure if
vue-demiversion was specifically set, but the mismatch betweenvue-i18n-routingand@intlify/vue-router-bridgemay be causing issues downstream in@nuxtjs/i18n. It seemsvue-demihardly if ever introduce breaking changes, using this version range will assume any newer version will be non breaking, perhaps this is too lenient?This branch should not be merged until intlify/bridging#50 has been merged and its version has been updated in the package file here.
Linked Issues
npmnuxt-modules/i18n#2556Additional context